PMoct: A Policy management tool for OCT based Design Systems for Multiple Domains

suit. This is because the policy is hard-coded In the associated design management tool, In this case, Specifying and maintaining the semantics of data used DMoct 131, [4]. It is even more difficult to use tools * by CAD/CAE tools is often accomplished through writand libraries that are not developed as part of the same ten documentation. This documentation is used by the suite of tools. To use tools from different suites tool developers and is not usually computer processrequires translators to be developed and used to map able which makes sharing of tools and libraries very the data from one policy to another. For example, using difficult and cumbersome. In the OCT data manageLager policy and the octtools policy requires the ment system developed at U.C Berkeley. the semantics siv2sym and sym2siv translators to allow designs pro* are referred to as the policy. In this paper, we describe duced using DMoct to use the TlmberWolf tools[5]. a set of tools that has been developed to allow the user This proliferation of policies does not foster the develto specify and store the semantics (or policy) itself in opment of sharable libraries, primarily because DMoct the database, and ensure that new instances that are would have to be modified or extended for new library added to the database will be semantically consistent. policies such as for PCBs (printed circuit boards) or MCMs (multi-chip modules).